<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN" "http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head>
    <title>Help - The Product Backlog Entry Page</title>
    <link rel="stylesheet" href="Style.css" />
</head>
<a href="default_help.htm">default_help.htm</a>
<body>
    <a href="Default_help.htm">
    <img border="0" src="../Images/Banner2_Web.png" />
    </a>
    <br /><br />
    
    <p class="header1">Product Backlog Entry Table</p>
    <p>This page allows you to enter new tasks into a product's backlog.</p>
    <hr />
    
    <p class="header2">Table Display Options</p>
    <img src="images/product_backlog_1.jpg" />
    
        <ul type="circle">
        <li><font class="header3">Product Dropdown</font> - This dropdown allows you to select which product's tasks to display in the table.</li>
        <li><font class="header3">State Dropdown</font> - This dropdown allows you to select whether the table will display active items, completed items or both.</li>
        <li><font class="header3">Page Size Dropdown</font> - This dropdown allows you to select how many tasks will be displayed per table page.</li>
        <li><font class="header3">New Backlog Entry Button</font> - This button will insert a new task into the table for the currently selected product.</li>
        </ul>
        
    <hr />
    
    <p class="header2">Column Descriptions</p>
    <img src="images/product_backlog_2.jpg" />
    
        <br /><br /><font class="note">Note: All underlined columns can be sorted on by clicking the column name.</font>
        <ul type="circle">
            <li><font class="header3">ID</font> - This column includes the unique numeric ID for this feature and cannot be edited.</li>
            <li><font class="header3">Product</font> - This column includes a dropdown list of proucts which this feature can be assigned to. This column is only available in edit mode.
            <li><font class="header3">Customer Scenario</font> - This column includes the name of the customer scenario from which this feature was generated. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Feature</font> - This column includes the name of the feature that tasks can be associated with.</li>
            <li><font class="header3">Activity</font> - This column includes the type of work this feature requires, for example development, testing or documentation. Individual tasks relating to this feature can be identified by entering them into this field in the following format: Task:Task_Description[owner/base_time]. The base time is in the units used for the product/master backlog.</li>
            <li><font class="header3">Description</font> - This column includes the description of the feature. </li>
            <li><font class="header3">Priority</font> - This column includes a numeric value indicating the priority of completing this feature without regard to other features. In general, this value is used like the priority field in Product Studio. For example priority one features should be completed this sprint, while priority two features can wait longer.</li>
            <li><font class="header3">Product Rank</font> - This column includes a numeric value indicating the rank of this feature against all other features for this product. For example, a feature with a rank of one should be completed before a feature of rank two. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Master Rank</font> - This column includes a numeric value indicating the rank of this feature against all other features for all products. For example, a feature with rank of one on this product should be completed before a feature of rank two on another product. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Hours/Weeks</font> - This column includes the number of hours/weeks it is expected to take to complete this feature. This column can be toggled between hours and weeks on the "Administer Scrum Teams" page. Note: When this column is displayed in weeks, the value will be displayed to three decimal points. This allows for the breakdown of time to all hours. For example, if the field is displayed in weeks, one hour would be 0.025. When the field is displayed in hours, only two decimals places are displayed. </li>
            <li><font class="header3">Complete</font> - This column includes a checkbox indicating whether all work for this feature has been completed.</li>
            <li><font class="header3">Show in MB</font> - This column includes a checkbox indicating whether the feature should be displayed in the master backlog page. This should be checked if a feature is being considered for inclusion in a sprint. Once the feature is added to the sprint this checkbox is automatically unchecked. This can be used to prevent a second team, working from the same product backlog, from including a duplicate feature in their sprint. If a feature is punted from a sprint this checkbox will be rechecked at sprint completion.</li>
            </ul>
        
    <hr />

    <p class="header2">Table Data Options</p>
    <img src="images/product_backlog_3.jpg" />
    
        <ul type="circle">
        <li><font class="header3">Re-number Product Rank</font> - This option resets the product rank value, starting at 1, based on the current product rank of the tasks in the table. </li>
        <li><font class="header3">Update Product Rank From Master Rank</font> - This option synchs the product rank value with the master rank value.</li>
        <li><font class="header3">Sort by Feature and Activity</font> - This option sorts by feature and then by activities within a feature.</li>
        <li><font class="header3">Set all Active to show in Master Backlog</font> - This option will set all non-completed items to show in the master backlog. </li>
        <li><font class="header3">Auto Product Rank</font> - This option will automatically update all other product's ranks, when a change is made to the selected product's rank.</li>
        <li><font class="header3">Auto Master Rank</font> - This option will automatically update all other master ranks, within this product, when a change is made to the selected master rank. </li>
        <li><font class="header3">Show Product Rank</font> - This option allows the user to turn on or off the display of the product rank column.</li>
        <li><font class="header3">Show Master Rank</font> - This option allows the user to turn on or off the display of the master rank column.</li>
        <li><font class="header3">Show Product (Edit Mode)</font> - This option allows the user to turn on or off the display of a product name dropdown when editing a task. This allows tasks to be moved between products.</li>
        <li><font class="header3">Show Customer Scenario</font> - This option allows the user to turn on or off the display of the customer scenario column.</li>
        </ul>
        
    <hr />
    
    <p class="header2">Adding a New Product Backlog Entry</p>
    <img src="images/product_backlog_4.jpg" />
   
        <ol> 
        <li>Click the "New Backlog Entry" button on the top of the page.</li>
        <li>A new row with default values will appear in the table.</li>
        <li>Enter the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">ID</font> - This column includes the unique numeric ID for this feature and cannot be edited.</li>
            <li><font class="header3">Product</font> - Select the product which this feature should be assigned to. This column is only available in edit mode.
            <li><font class="header3">Customer Scenario</font> - Enter the name of the customer scenario from which this feature was generated. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Feature</font> - Enter the name of the feature that tasks can be associated with.</li>
            <li><font class="header3">Activity</font> - Enter the type of work this feature requires, for example development, testing or documentation. </li>
            <li><font class="header3">Description</font> - Enter the description of the feature. Individual tasks relating to this feature can be identified by entering them into this field in the following format: Task:Task_Description[owner/base_time]. The base time is in the units used for the product/master backlog.</li>
            <li><font class="header3">Priority</font> - Enter a numeric value indicating the priority of completing this feature without regard to other features. In general, this value is used like the priority field in Product Studio. For example priority one features should be completed this sprint, while priority two features can wait longer.</li>
            <li><font class="header3">Product Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for this product. For example, a feature with a rank of one should be completed before a feature of rank two. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Master Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for all products. For example, a feature with rank of one on this product should be completed before a feature of rank two on another product. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Hours/Weeks</font> - Enter the number of hours/weeks it is expected to take to complete this feature. This column can be toggled between hours and weeks on the "Administer Scrum Teams" page. Note: When this column is displayed in weeks, the value will be displayed to three decimal points. This allows for the breakdown of time to all hours. For example, if the field is displayed in weeks, one hour would be 0.025. When the field is displayed in hours, only two decimals places are displayed.</li>
            <li><font class="header3">Complete</font> - Select whether all work for this feature has been completed.</li>
            <li><font class="header3">Show in MB</font> - Select whether the feature should be displayed in the master backlog page. This should be checked if a feature is being considered for inclusion in a sprint. Once the feature is added to the sprint this checkbox is automatically unchecked. This can be used to prevent a second team, working from the same product backlog, from including a duplicate feature in their sprint. If a feature is punted from a sprint this checkbox will be rechecked at sprint completion.</li>
            </ul>
        </li>
        <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
        <li>If you select cancel, the new row will be automatically deleted.</li>
        </ol>
    
    <hr />
    
    <p class="header2">Editing a Product Backlog Entry</p>
    <img src="images/product_backlog_4.jpg" />
       <ol> 
        <li>Click "Edit" in the row of the table you wish to edit.</li>
        <li>Edit the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">ID</font> - This column includes the unique numeric ID for this feature and cannot be edited.</li>
            <li><font class="header3">Product</font> - Select the product which this feature should be assigned to. This column is only available in edit mode.
            <li><font class="header3">Customer Scenario</font> - Enter the name of the customer scenario from which this feature was generated. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Feature</font> - Enter the name of the feature that tasks can be associated with.</li>
            <li><font class="header3">Activity</font> - Enter the type of work this feature requires, for example development, testing or documentation. </li>
            <li><font class="header3">Description</font> - Enter the description of the feature. Individual tasks relating to this feature can be identified by entering them into this field in the following format: Task:Task_Description[owner/base_time]. The base time is in the units used for the product/master backlog.</li>
            <li><font class="header3">Priority</font> - Enter a numeric value indicating the priority of completing this feature without regard to other features. In general, this value is used like the priority field in Product Studio. For example priority one features should be completed this sprint, while priority two features can wait longer.</li>
            <li><font class="header3">Product Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for this product. For example, a feature with a rank of one should be completed before a feature of rank two. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Master Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for all products. For example, a feature with rank of one on this product should be completed before a feature of rank two on another product. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Hours/Weeks</font> - Enter the number of hours/weeks it is expected to take to complete this feature. This column can be toggled between hours and weeks on the "Administer Scrum Teams" page. Note: When this column is displayed in weeks, the value will be displayed to three decimal points. This allows for the breakdown of time to all hours. For example, if the field is displayed in weeks, one hour would be 0.025. When the field is displayed in hours, only two decimals places are displayed.</li>
            <li><font class="header3">Complete</font> - Select whether all work for this feature has been completed.</li>
            <li><font class="header3">Show in MB</font> - Select whether the feature should be displayed in the master backlog page. This should be checked if a feature is being considered for inclusion in a sprint. Once the feature is added to the sprint this checkbox is automatically unchecked. This can be used to prevent a second team, working from the same product backlog, from including a duplicate feature in their sprint. If a feature is punted from a sprint this checkbox will be rechecked at sprint completion.</li>
            </ul>
        </li>
        <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
        </ol>
     <hr />
     
     <p class="header2">Copying a Product Backlog Entry</p>
     <img src="images/product_backlog_4.jpg" />
       <ol> 
        <li>Click "Copy" in the row of the table you wish to copy.</li>
        <li>A new entry will be created in the table with duplicate values.</li>
        <li>Edit the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">ID</font> - This column includes the unique numeric ID for this feature and cannot be edited.</li>
            <li><font class="header3">Product</font> - Select the product which this feature should be assigned to. This column is only available in edit mode.
            <li><font class="header3">Customer Scenario</font> - Enter the name of the customer scenario from which this feature was generated. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Feature</font> - Enter the name of the feature that tasks can be associated with.</li>
            <li><font class="header3">Activity</font> - Enter the type of work this feature requires, for example development, testing or documentation. </li>
            <li><font class="header3">Description</font> - Enter the description of the feature. Individual tasks relating to this feature can be identified by entering them into this field in the following format: Task:Task_Description[owner/base_time]. The base time is in the units used for the product/master backlog.</li>
            <li><font class="header3">Priority</font> - Enter a numeric value indicating the priority of completing this feature without regard to other features. In general, this value is used like the priority field in Product Studio. For example priority one features should be completed this sprint, while priority two features can wait longer.</li>
            <li><font class="header3">Product Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for this product. For example, a feature with a rank of one should be completed before a feature of rank two. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Master Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for all products. For example, a feature with rank of one on this product should be completed before a feature of rank two on another product. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Hours/Weeks</font> - Enter the number of hours/weeks it is expected to take to complete this feature. This column can be toggled between hours and weeks on the "Administer Scrum Teams" page. Note: When this column is displayed in weeks, the value will be displayed to three decimal points. This allows for the breakdown of time to all hours. For example, if the field is displayed in weeks, one hour would be 0.025. When the field is displayed in hours, only two decimals places are displayed.</li>
            <li><font class="header3">Complete</font> - Select whether all work for this feature has been completed.</li>
            <li><font class="header3">Show in MB</font> - Select whether the feature should be displayed in the master backlog page. This should be checked if a feature is being considered for inclusion in a sprint. Once the feature is added to the sprint this checkbox is automatically unchecked. This can be used to prevent a second team, working from the same product backlog, from including a duplicate feature in their sprint. If a feature is punted from a sprint this checkbox will be rechecked at sprint completion.</li>
            </ul>
        </li>
         <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
       </ol>
       <hr />
       
     <p class="header2">Spliting a Product Backlog Entry</p>
     <img src="images/product_backlog_4.jpg" />
       <ol> 
        <li>Click "Split" in the row of the table you wish to split.</li>
        <li>A new entry will be created in the table with duplicate values, but the hours/weeks in both the original entry and the new entry will be cut in half.</li>
        <li>Edit the data in the columns, according to their descriptions below:
            <ul type="circle">
            <li><font class="header3">ID</font> - This column includes the unique numeric ID for this feature and cannot be edited.</li>
            <li><font class="header3">Product</font> - Select the product which this feature should be assigned to. This column is only available in edit mode.
            <li><font class="header3">Customer Scenario</font> - Enter the name of the customer scenario from which this feature was generated. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Feature</font> - Enter the name of the feature that tasks can be associated with.</li>
            <li><font class="header3">Activity</font> - Enter the type of work this feature requires, for example development, testing or documentation. </li>
            <li><font class="header3">Description</font> - Enter the description of the feature. Individual tasks relating to this feature can be identified by entering them into this field in the following format: Task:Task_Description[owner/base_time]. The base time is in the units used for the product/master backlog.</li>
            <li><font class="header3">Priority</font> - Enter a numeric value indicating the priority of completing this feature without regard to other features. In general, this value is used like the priority field in Product Studio. For example priority one features should be completed this sprint, while priority two features can wait longer.</li>
            <li><font class="header3">Product Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for this product. For example, a feature with a rank of one should be completed before a feature of rank two. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Master Rank</font> - Enter a numeric value indicating the rank of this feature against all other features for all products. For example, a feature with rank of one on this product should be completed before a feature of rank two on another product. This column may be turned off in the options at the bottom of the table.</li>
            <li><font class="header3">Hours/Weeks</font> - Enter the number of hours/weeks it is expected to take to complete this feature. This column can be toggled between hours and weeks on the "Administer Scrum Teams" page. Note: When this column is displayed in weeks, the value will be displayed to three decimal points. This allows for the breakdown of time to all hours. For example, if the field is displayed in weeks, one hour would be 0.025. When the field is displayed in hours, only two decimals places are displayed.</li>
            <li><font class="header3">Complete</font> - Select whether all work for this feature has been completed.</li>
            <li><font class="header3">Show in MB</font> - Select whether the feature should be displayed in the master backlog page. This should be checked if a feature is being considered for inclusion in a sprint. Once the feature is added to the sprint this checkbox is automatically unchecked. This can be used to prevent a second team, working from the same product backlog, from including a duplicate feature in their sprint. If a feature is punted from a sprint this checkbox will be rechecked at sprint completion.</li>
            </ul>
        </li>
         <li>Click "Update" to change the values for the row in the database, or click "Cancel" to discard the changes.</li>
       </ol>
       <hr />
         
     <p class="header2">Deleting a Product Backlog Entry</p>
       <ol> 
        <li>Click "Delete" in the row of the table you wish to delete.</li>
        <li>Click "OK" in the dialog box that appears to delete the product, otherwise click "Cancel"</li>
       </ol>
</body>

</html>
